Description

Follow up to #12990 to fix a eslint warning in our React hooks for Sandcastle.

This change shouldn't affect functionality at all. if anything it may have a very minor improvement for performance during re-renders.

We may want to turn off --quiet mode on eslint since we don't actually have any warnings but that's a separate discussion.

Issue number and link

no issue

Testing plan

• Run npx eslint "./**/*.js" "./**/*.cjs" "./**/*.html" to make sure no errors or warnings show up
• Sandcastle should operate exactly as it does now. maybe slightly better performance
• Check that loading sandcastles, running them and re-running them all work as expected

Author checklist

• I have submitted a Contributor License Agreement
• I have added my name to CONTRIBUTORS.md
• I have updated CHANGES.md with a short summary of my change
• I have added or updated unit tests to ensure consistent code coverage
• I have updated the inline documentation, and included code examples where relevant
• I have performed a self-review of my code